docs: overview: Explicitly call out dpkg/rpm
authorColin Walters <walters@verbum.org>
Fri, 20 Jun 2014 14:11:42 +0000 (10:11 -0400)
committerColin Walters <walters@verbum.org>
Fri, 20 Jun 2014 14:11:42 +0000 (10:11 -0400)
To be more clear that we don't handle "inventory".

doc/overview.xml

index 79763b5e6563f5bee8d7ef4fd43a9d6fe836f418..f2273068f1541300db55d8fa778cbea5fbb69f63 100644 (file)
       <emphasis>complete</emphasis> (bootable) filesystem trees.  It
       has no built-in knowledge of how a given filesystem tree was
       generated or the origin of individual files, or dependencies,
-      descriptions of individual components.  This means that, for
-      example, if you are distributing software which is licensed
-      under the GNU General Public License, the burden lies with the
-      tool generating these filesystem trees to ensure sufficent
-      metadata is included for compliance.
+      descriptions of individual components.  Put another way, OSTree
+      only handles delivery and deployment; you will likely still want
+      to include inside each tree metadata about the individual
+      components that went into the tree.  For example, a system
+      administrator may want to know what version of OpenSSL was
+      included in your tree, so you should support the equivalent of
+      <command>rpm -q</command> or <command>dpkg -L</command>.
     </para>
     <para>
       The OSTree core emphasizes replicating read-only OS trees via